Building AI Knowledge Bases That Actually Work with Claude
This post picks up where my 8th February entry on Knowledge Bases left off (link). This time the focus is practical: how to set one up specifically for Claude, either on your local machine or through Google Drive.
How to Build a Personal Knowledge Base for Claude
Every time you start a new conversation with Claude, it starts completely fresh. It does not hold a memory of what you told it last week, without knowledge of your specific workflows, terminology, or processes unless you provide it. For most users, that means re-explaining the same things session after session.
A personal KB can solve this. Instead of re-briefing Claude every time, you build a set of well-structured documents and point Claude to them at the start of each session. The difference in response quality is significant.
This guide covers how to set it up properly: the right format, how to organise your files, how to write documents Claude can actually use, and how to connect everything through Google Drive.
What Is a Personal Knowledge Base for Claude?
It's a structured collection of documents that contain your own knowledge and your processes, frameworks, terminology, checklists, and reference material. Everything written in a way that Claude can read and retrieve from quickly.
Note, this is different from what enterprises do with RAG pipelines and vector databases. For personal use, it's simpler: a set of well-organised text files that you upload to Claude at the start of a session, or that Claude pulls from your Google Drive automatically if you connect it.
The principle is the same: Claude is only as good as what you give it. A good KB turns Claude from a smart generalist into a well-briefed specialist who already knows how you work.
Choosing the Right Format
Not all file formats are equal. Claude reads structured text well and layout-heavy formats poorly.
Best options:
Markdown (.md) — The best choice for documents you write yourself. Lightweight, perfectly structured, and Claude reads it cleanly. Any text editor works.
Plain Text (.txt) — Good for simple lists and quick references.
Google Docs — The best choice if you store your knowledge base in Google Drive. Native format, Claude reads it best through the Drive connector.
Avoid:
Scanned PDFs — Claude reads text, not images of text
Don't dump PDFs and hope for the best
Spreadsheets as your main knowledge documents
Image-heavy Word documents
Folder Structure
Keep one topic per file and one file per topic. That's the core rule. Beyond that, organize by category with numbered folders so they sort in a predictable order. Also, adapt the folder names to your field. The structure is what matters, not the labels, because when Claude searches your Drive, it matches on document names and content.
Use: google-ads-campaign-framework.md
Do not use: notes-final-v3-FINAL.md
See example below:
📁 My-Knowledge-Base/
│
├── 📁 00-Index/
│ └── master-index.md
│
├── 📁 01-Processes/
│ ├── workflow-a.md
│ └── workflow-b.md
│
├── 📁 02-Tools-and-Resources/
│ └── tools-reference.md
│
├── 📁 03-Checklists/
│ └── task-checklist.md
│
├── 📁 04-Case-Studies/
│ └── template.md
│
└── 📁 05-References/
├── glossary.md
└── external-links.md
How to Write Documents Claude Can Actually Use
This is where most people go wrong. The way you write your documents directly affects how well Claude navigates and retrieves from them. My suggestion: use the below approach as your starting point for every and each document from you KB:
1. Document Title
Category: [Process / Tool / Reference / Checklist]
Topic:[Specific subject]
Keywords:[comma-separated: term1, term2, term3]
Last Updated: YYYY-MM-DD
2. Summary
2–3 sentences describing what this document covers,
written as if explaining to someone searching for it.
3. [Main Section]
Content here.
4. [Another Section]
Content here.
5. Quick Reference
- Most important point
- Second most important point
6. Related Documents
path/to/related-doc.md
Best Practices
Put the most important information at the top. Claude weighs early content heavily. Your Summary and Quick Reference sections are the first things it will use to understand what the document is about.
Use headers. Claude navigates by section headers. A document with clear structure is like a well-indexed file — Claude jumps to the relevant section rather than reading everything.
Be specific. "Use Ahrefs for backlink analysis" is useful. "There are various SEO tools available" is not. The more precise your writing, the more precise Claude's responses.
Add a Keywords line. When you ask Claude a question, it matches your words to document content. A keywords line ensures Claude finds the right document even when you use different terminology.
Cross-reference related documents. A "Related Documents" section at the bottom helps Claude pull from multiple sources when answering complex questions.
The Most Important File: The Master Index
The master index is a single document that maps your entire knowledge base. Think of it as a table of contents for a book. This is the first file you give Claude in every session. Important: Update this file every time you add a new document. An outdated master index means Claude won't know a document exists.
A good master index looks like this:
My Knowledge Base - Master Index
Last Updated: 2026-04-05
1.What This Covers
[2–3 sentences describing the whole knowledge base]
2. Document Map
3. Processes
- 01-Processes/workflow-a.md` — What this file covers
- 01-Processes/workflow-b.md` — What this file covers
4. Tools
- 02-Tools/tools-reference.md` — What this file covers
5. Keyword Quick Reference
If you ask about... Point Claude to...
Topic A] 01-Processes/workflow-a.md
Topic B 02-Tools/tools-reference.md
Setting Up on Google Drive
Google Drive gives you two advantages: access from any device, and direct integration with Claude, what does it means? Claude can search your Drive automatically without you uploading anything manually.
Method A: Manual Upload
Download the files you need from Drive, then upload them to Claude using the paperclip icon in the chat. Works immediately, no setup required.
Best for: occasional use or documents you don't want permanently connected.
Method B: Google Drive Connector
Connect your Google Drive to Claude once, and ask Claude to search it automatically in any conversation. Follow the below steps to set up your Google Drive Connector:
Step 1 — Create your folder structure in Google Drive
Go to drive.google.com → click "+ New" → "New Folder" → name it My-Knowledge-Base. Then create your subfolders inside it.
Step 2 — Create your documents in Google Docs format
Inside each subfolder, click "+ New" → "Google Docs". Write your documents directly there. Google Docs is the native format for Drive and what Claude reads best through the connector.
Step 3 — Connect Google Drive to Claude
Go to claude.ai → Settings → Integrations → find Google Drive → click "Connect". Sign in with your Google account and grant permission. This is a one-time step.
Step 4 — Keep your folder private
Right-click your knowledge base folder in Drive → "Share" → confirm it says "Restricted" (only you). Your knowledge base should be private by default.
Step 5 — Test the connection
Open a new Claude conversation and try this prompt:
"Search my Google Drive for my knowledge base and read the master index first. Then use those documents as your primary reference for this entire session."
If Claude finds and summarises your master index, the connection is working.
Other Prompts That Work
1.At the start of any session (Drive connected)
"Search my Google Drive for my knowledge base and read the master index first. Use those documents as your primary reference for this entire conversation."
2. For a specific task
"Check my Google Drive knowledge base for my document on [topic] and use it to help me [task]. Follow the process exactly as I've written it."
3. Manual upload version
"I've uploaded my knowledge base documents. Read all of them and use them as your primary reference. Prioritise these documents over your general training where they conflict."
4. Adding new documents
"I just learned something new about [topic]. Help me write a new document in the correct format for my knowledge base. Match the same template structure as my other documents."
Practical Tips
Start small. Don't try to document everything on day one. Start with your three most-used topics and your master index. Add a new document every time you find yourself re-explaining the same thing to Claude more than once.
Date every document. Always include a "Last Updated" date at the top. When you're working with multiple documents, this tells Claude which information is current.
Write for retrieval, not for reading. Your knowledge base documents are reference material, not essays. Bullet points, numbered steps, tables, and headers are more useful than paragraphs of prose.
Review quarterly. Set a reminder every three months to update, remove outdated documents, and add new topics. A knowledge base that isn't maintained becomes noise.
Use Obsidian if you prefer local files. If you'd rather not use Google Drive, Obsidian (obsidian.md) is the best local alternative. It's free, works with plain Markdown files on your computer, and has strong search and linking between documents. Export your notes as Markdown files and upload them to Claude as needed.